![require(esm) Backported to Node.js 20, Paving the Way for ESM-Only Packages](https://cdn.sanity.io/images/cgdhsj6q/production/be8ab80c8efa5907bc341c6fefe9aa20d239d890-1600x1097.png?w=400&fit=max&auto=format)
Security News
require(esm) Backported to Node.js 20, Paving the Way for ESM-Only Packages
require(esm) backported to Node.js 20, easing the transition to ESM-only packages and reducing complexity for developers as Node 18 nears end-of-life.
node-loggly-bulk
Advanced tools
A client implementation for Loggly in node.js. Check out Loggly's Node logging documentation for more.
The node-loggly-bulk
library is compliant with the Loggly API. Using node-loggly-bulk
is easy for a variety of scenarios: logging, working with devices and inputs, searching, and facet searching.
Before we can do anything with Loggly, we have to create a client with valid credentials. We will authenticate for you automatically:
var loggly = require('node-loggly-bulk');
var client = loggly.createClient({
token: "your-really-long-input-token",
subdomain: "your-subdomain",
auth: {
username: "your-username",
password: "your-password"
},
//
// Optional: Tag to send with EVERY log message
//
tags: ['global-tag']
});
There are two ways to send log information to Loggly via node-loggly-bulk. The first is to simply call client.log with an appropriate input token:
client.log('127.0.0.1 - Theres no place like home', function (err, result) {
// Do something once you've logged
});
Note that the callback in the above example is optional, if you prefer the 'fire and forget' method of logging:
client.log('127.0.0.1 - Theres no place like home');
If you're using Loggly's tags functionality, simply include an array of tags as the second argument to the log
method:
client.log('127.0.0.1 - Theres no place like home', [ 'dorothy' ], function (err, result) {
// Do something once you've logged
});
note Tags passed into the log function will be merged with any global tags you may have defined.
In addition to logging pure strings it is also possible to pass shallow JSON object literals (i.e. no nested objects) to client.log(..) or input.log(..) methods, which will get converted into the Loggly recommended string representation. So
var source = {
foo: 1,
bar: 2,
buzz: 3
};
input.log(source);
will be logged as:
foo=1,bar=2,buzz=3
It is also possible to log complex objects using the new JSON capabilities of Loggly. To enable JSON functionality in the client simply add 'json: true' to the configuration:
var config = {
subdomain: "your-subdomain",
auth: {
username: "your-username",
password: "your-password"
},
json: true
};
When the json flag is enabled, objects will be converted to JSON using JSON.stringify before being transmitted to Loggly. So
var source = {
foo: 1,
bar: 2,
buzz: {
sheep: 'jumped',
times: 10
}
};
input.log(source);
will be logged as:
{ "foo": 1, "bar": 2, "buzz": {"sheep": "jumped", "times": 10 }}
It is possible to send arrays, which will result in one single request to Loggly.
input.log([ {iam:'number 1'}, {iam:'number 2'} ])
Searching with node-loggly-bulk is easy. All you have to do is use the search() method defined on each Loggly client:
var util = require('util');
client.search('404', function (err, results) {
// Inspect the result set
console.dir(results.events);
});
The search() method can also take an Object parameter that allows you to set additional search parameters such as: rows, from, until, etc.
var util = require('util');
client.search({ query: '404', rows: 10 })
.run(function (err, results) {
// Inspect the result set
console.dir(results.events);
});
See the Loggly search guide for more details on how to effectively search through your Loggly logs.
$ curl http://npmjs.org/install.sh | sh
$ npm install node-loggly-bulk
All of the node-loggly-bulk tests are written in vows, and cover all of the use cases described above. You will need to add your Loggly username, password, subdomain, and your loggly token to test/config.json before running tests.
{
"token": "your-really-long-token-you-got-when-you-created-an-http-input",
"subdomain": "your-subdomain",
"auth": {
"username": "your-username",
"password": "your-password"
}
}
Once you have valid Loggly credentials you can run tests with vows:
$ npm test
To mock the HTTP requests and run test cases in your local machine you can run the following command
$ npm run test-as-mock
FAQs
A client implementation for Loggly cloud Logging-as-a-Service API
The npm package node-loggly-bulk receives a total of 96,939 weekly downloads. As such, node-loggly-bulk popularity was classified as popular.
We found that node-loggly-bulk demonstrated a healthy version release cadence and project activity because the last version was released less than a year ago. It has 2 open source maintainers collaborating on the project.
Did you know?
Socket for GitHub automatically highlights issues in each pull request and monitors the health of all your open source dependencies. Discover the contents of your packages and block harmful activity before you install or update your dependencies.
Security News
require(esm) backported to Node.js 20, easing the transition to ESM-only packages and reducing complexity for developers as Node 18 nears end-of-life.
Security News
PyPI now supports iOS and Android wheels, making it easier for Python developers to distribute mobile packages.
Security News
Create React App is officially deprecated due to React 19 issues and lack of maintenance—developers should switch to Vite or other modern alternatives.